-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process api hook #2131
Process api hook #2131
Conversation
let assemblies = assemblies |> Seq.toArray | ||
let details = assemblies |> String.separated ", " | ||
use __ = Trace.traceTask "NUnit" details | ||
let p = createProcess setParams assemblies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could this not be
createProcess setParams assemblies
|> Proc.run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes indeed
Simplify command line when quotes are not required
@@ -11,14 +11,15 @@ let fsCheckConfig = { FsCheckConfig.defaultConfig with maxTest = 1000 } | |||
[<Tests>] | |||
let tests = | |||
testList "Fake.Core.Process.Tests" [ | |||
testPropertyWithConfig fsCheckConfig "toWindowsCommandLine is the inverse of fromWindowsCommandLine" <| | |||
//Process.setEnableProcessTracing true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this line is uncommented it completely breaks the "fake-context" for some reason and about the half (around 30) tests start to fail... Would be interesting to figure out why.
Note that not only tests in this file start failing but everywhere (especially the FakeVar
and Context
ones)
Description
Use the new API in order to write unit-tests